Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

Client Logging (-clientlog)

Use Client Logging (-clientlog) to allow an application to automatically write error and warning messages to the specified log file.

Operating system and syntax	UNIX Windows	-clientlog filename
Use with	Maximum value	Minimum value	Single-user default	Multi-user default
Client Session	–	–	–	–

filename

The name of log file OpenEdge uses for messages and 4GL stack trace information.

If the filename you supply is a relative pathname, then a file is accessed relative to the current working directory. If the filename is an absolute pathname, then the specified file is accessed.

Note: Do not include a numbered sequence in the filename. This might conflict with the rolled over log files OpenEdge creates based on your Number of Log Files to Keep (-numlogfiles) and Log Threshold (-logthreshold) startup parameter settings.

Use the Log Entry Types (-logentrytypes) startup parameter to specify one or more types of log entries you want to write to the log file. Use the Logging Level (-logginglevel) startup parameter to specify the level at which log entries are written to the log file.

When you use the -clientlog startup parameter, and you also specify the Debug Alert (-debugalert) startup parameter or set SESSION:DEBUG-ALERT to yes, the log includes a 4GL stack trace for each log entry.

If an error message is diverted to the ERROR-STATUS system handle, and client logging is enabled, then no information is written to the log file.

In a non-interactive session, the application is configured so that the output device is associated with a file (or another device). In this configuration, when a Progress statement encounters an error, it writes the error to the output device. If client logging is enabled, then this message is also written to the specified log file. Errors are written to the output device at logging level 1 (Error) and up.

You can use the MESSAGE statement with the VIEW-AS ALERT-BOX option to write application specific information to the screen and the log file. In this case, you must specify an entry type of “4GLMessages” and a logging level of 2 (Basic), at least.

For more information about logging levels, see the Logging Level (-logginglevel) startup parameter reference entry. For more information about specifying log entry types, see the Log Entry Types (-logentrytypes) startup parameter reference entry.

You can also use attributes on the LOG-MANAGER system handle to specify log entry types and logging levels.

For more information about the Progress 4GL language elements referenced above, see the OpenEdge Development: Progress 4GL Reference .

When -debug-alert is on and an error occurs in a batch session for:

A 4GL batch client, Progress records the 4GL stack trace information in the log file specified with -clientlog. In this case, Progress lists the stack trace information in reverse order. That is, the procedure that generated the error is written first, and the root procedure is written last.
An AppServer client or a WebSpeed® agent, Progress records the 4GL stack trace information in their respective log files, also in reverse order. If you view one of these log files in the Progress Explorer, it appears in top-down order since Explorer displays log files in reverse order.

The code page used for the log file is -cpinternal and no conversions are performed for these log files.

For more detailed information about enabling logging, see OpenEdge Development: Debugging and Troubleshooting .